Using Degree of Impact on Software Artifacts to define priority for handling Inconsistencies

In development process developers need to prioritize inconsistencies to identify the actions taken to handle inconsistency and to measure the impact of inconsistency-handling actions which is a key to effective action in the presence of inconsistencies. However, different stakeholders may assign different levels of priority to the same shared requirements from their own perspectives. The disagreement in the levels of priority assigned to the same shared requirements often puts developer in dilemma during the inconsistency handling. In this paper we define different algorithms for: measuring degree of impact on software artifacts; defining the ranges level using minimum and maximum values of degree of impact on software artifacts; identifying priority of handling and assessing the degree of risk and selecting handling actions depending on priority level defined whether it to resolve inconsistencies immediately or ameliorate or circumvent or ignore. These algorithms define levels of priority systematically to identify the different actions taken for handling inconsistency without depending on stakeholder perspective.